home *** CD-ROM | disk | FTP | other *** search
- Path: newsfeed.internetmci.com!xmission!news
- From: jsburger@xmission.com (John S. Burger)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Re: Another THOR problem
- Date: 20 Jan 96 14:30:06 +0500
- Organization: XMission Internet (801 539 0900)
- Message-ID: <3021.6593T870T333@xmission.com>
- References: <626.6587T629T1294@ibm.net> <704.6590T749T1701@icenet.no> <1717.6592T910T1133@ibm.net>
- NNTP-Posting-Host: slc3.xmission.com
- X-Newsreader: THOR 2.22 (Amiga;TCP/IP)
-
-
- On or about 19-Jan-96 19:22:37 Georges Heinesch typed the following words
- about "Re: Another THOR problem". My reply is thus...
-
-
- GH> In a message of 17-Jan-96 12:29:34, Petter Nilsen wrote:
-
- >>> Failed to load the configuration datafiles.
- >>> Error in: Comms:Internet/THOR/Data/BBS.data.
- >>> Cause: Dos failure.
- >>> IoErr reports: 103.
-
- >>Fault 103: not enough memory available
-
- >>You're out of memory.
-
- GH> ;)
-
- GH> Sorry. I actually forgot to mention that this was not the reason.
-
- GH> I had another 6 MB RAM left. But the problem was that the 8n1.device srew
- GH> everything up.
-
- GH> Here the story:
-
- GH> I was one of the Amiga users, who always said that the 8n1.device was
- GH> stable like a rock and faster than the baudbandit.device and the
- GH> standard serial.device. I used the 8n1.device with Term 4.5, TrapDoor,
- GH> TrapFax and many other applications. I read about the problems others had
- GH> with 8n1.device while here, 8n1 was the only device which was able to mak
- GH> 57600 without errors.
-
- GH> I used the 8n1.device with AmiTCP and all of a sudden, the problems
- GH> started. I tried to trace the faulty code. Initially I thought, it would
- GH> AmiTCP itself, later on inetd, then GetTCP (THOR), then PowerSnap or
- GH> another code from WBStartup. Enforcer never traced the 8n1.device!
-
- GH> Now that I replaced it again with the serial.device (with 38400),
- GH> everything works fine (after 3 month of random errors, lots of testing
- GH> telephone calls and many lost hours).
-
- Glad to see a died in the wool 8n1.device user finally see the light. :<) I
- have tried 8n1 off and on ever since it came out and always had crashes. Never
- right away but if I stayed connected long enough the machine would always
- crash. Stop using 8n1 and the crashes stoped. I always went back to
- serial.device and really couldn't see much difference in speed. BTW, I use
- serial.device on this machine (A2000, A2630@25mhz) at 57600 without priblems.
- I have just recently started using artser.device at 57600. It seems to be a
- little bit faster.
-
- GH> So my advice !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
- GH> Delete 8n1.device right away or keep in mind, that it might create
- GH> unpredictable memory disasters, which SegTracker and Enforcer will not
- GH> trace !
-
- GH> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
- I agree!!!
-
-
- --
- // -= John =- jsburger@xmission.com BIX: jburger
- \X/ Via
- Amateur Radio KB0ES T
- Amiga 2000 H
- A2630 A2632 John S. Burger Hooper, UT O
- 2+14megs RAM R
- 850meg HD This message was composed on... 2.22
- 20-Jan-96 14:23:44 MST
- --
-
- A truly wise man never plays leapfrog with a Unicorn.
-
-